An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

My app is rejected under Guideline 2.3.6 because the Age Rating answer for "Messaging and Chat" is "No". The reviewer says the app includes messaging and chat. I want to understand what the guideline means before I change the answer. What the app does: It is a companion app for families of a martial arts school (a business). Parents sign in to see their child's schedule, billing, and so on. A signed-in adult can send a message only to their own school. They never choose a recipient and can never reach another family or any other user of the app. The school's staff reply from somewhere else (the school's website), not from inside this app. Teen accounts (ages 13 to 17) are created by the school at a parent's request. They have no messaging at all. The Messages tab is not shown to them, and our server refuses any message from them. The app uses the Declared Age Range API to meet Texas age assurance requirements. My question: Does a feature that only lets a user contact the business providing the service, and never another user of the app, count as "Messaging and Chat" for the Age Rating? Or does that capability apply only to user-to-user communication? I had understood the capability to mean users messaging other users. If the answer is that any in-app message form counts, I will change the rating to "Yes". I just want to be sure I understand the definition, since the App Store Connect help text for that question is short. Has anyone been through this with a "contact the business" or support-style message feature? I asked the reviewer, but they pointed me here, since they "are not able to provide feedback on app concepts or features". Thank you.

Our first iOS app, Inosace Sleep, version 1.0, has been in "Waiting for Review" since October 29, 2026 (14 days). The review hasn't started and we haven't received any messages from App Review. What we've tried so far: Requested an expedited review on November 5. Apple confirmed it, but the status hasn't changed. Contacted Developer Support on November 7 (case ID 30000008149224), no reply yet. All agreements, tax and banking information are active in App Store Connect, and nothing has been changed since the submission. Is there anything else we can do, or could someone from Apple take a look?

Hello Apple App Review Team, I'm reaching out because I'm genuinely concerned that there may be an issue with my Apple Developer account or the review process associated with it. During my previous app submission, I initially assumed the delay was normal and that waiting another 3–4 days would resolve it. Unfortunately, the app remained stuck for nearly two weeks before the situation was finally addressed. Now, I'm experiencing a similar situation again. My latest submission entered "Waiting for Review" on November 12, 2026, at 8:20 AM. As of November 14, 2026, at 9:10 PM, more than 60 hours have passed without any progress or communication. I understand that Apple aims to review 90% of submissions within 48 hours and that some reviews naturally take longer. However, after experiencing a delay of nearly two weeks previously, I'm worried that simply continuing to wait may lead to the same situation again. My biggest concern is whether there might be an underlying issue with my Apple Developer account, submission records, or review queue that is repeatedly preventing my apps from being reviewed in a timely manner. I'm not just asking for my current app to be reviewed faster. I'm hoping someone from Apple can help investigate whether there is a recurring issue affecting my account. Could the App Review team please help check: Whether there are any account-level issues, restrictions, or technical problems affecting my submissions. Whether my current submission is correctly placed in the review queue. Whether anything is preventing my apps from entering the review process normally. If possible, I would sincerely appreciate having this investigated or escalated to the appropriate team. I'm concerned about experiencing another prolonged delay without knowing whether something is wrong or whether any action is required from me. Submission ID：bfa4f9c6-ce77-4884-a2c6-3b4aedf31356 Thank you for your time and assistance. I would really appreciate any help in understanding and resolving this situation.

Hello, I'm reaching out regarding an ongoing issue with an iOS application that has been stuck in the "In Review" status since October 26, 2026. As of today, November 13, the application has been in review for 18 days without any updates, rejection notices, requests for additional information, or communication explaining the delay. I've published multiple applications through the App Store before, and while I understand that review times can vary, I've never experienced anything remotely close to this. I've reached out to Apple Developer Support multiple times, sent approximately five emails, and even spent nearly three hours on hold trying to speak with someone who could provide some information. I've also submitted an expedited review request, which unfortunately hasn't resulted in any progress either. I even spoke with a support representative who mentioned that they would try to push the issue forward, but despite all these attempts, I still haven't received any meaningful updates or explanations. This delay has significantly affected my business, and it's incredibly frustrating to have an application sitting in review for this long without knowing what's happening or whether anything is actually being done. I completely understand that certain applications might require additional review time, and I have no issue with that. However, I would at least expect some form of communication, especially after nearly three weeks and multiple attempts to contact support. At this point, I'm genuinely concerned that the application might be stuck in Apple's review system or that something has gone wrong internally. Has anyone experienced a similar situation where an application remained specifically in "In Review" for this long? Is there any way to reach someone directly from the App Review team or escalate this beyond the standard support channels? I've already tried requesting an expedited review without success, so I'm unsure what other options are available. I'd appreciate any guidance or assistance, especially from someone at Apple who might be able to look into this. Thank you.

Hey everyone, We have a critical update for our app (Hook - AI Rizz Wingman) that has been stuck in "Waiting for Review" for over 10 days now across resubmissions, without moving to "In Review". This release includes urgent fixes and core product updates that are currently holding up our rollout. We've already checked the Resolution Center and there are no open messages or pending actions on our end. Has anyone else experienced this kind of delay recently? Beyond submitting an expedited review request, is there anything else that actually helps get a stuck build moving again? (In case anyone from the App Review team is browsing the forums and can take a look, here are the app details: Bullet App Name: Hook - AI Rizz Wingman  Bullet Apple ID: 6766006483  Bullet Bundle ID: com.hook.eden  Bullet SKU: 0001)  Thanks in advance for any insights

Hi everyone - I'm new to iOS development and about to launch my first app, so apologies if this is a basic question. The app has one yearly auto-renewable subscription with a free trial. I'd like my TestFlight testers to be able to use everything for free while they try out new versions. From what I've read, TestFlight and App Review both use the sandbox, so the app can't tell a tester from a reviewer while it runs. Apple's receipt validation article says to use the sandbox "while your app is in review". If I've got that wrong, please let me know. These are the options I've come up with: Two builds from the same code: one for TestFlight with the subscription turned off, and one with it on that goes to App Review and the App Store. One build. Testers subscribe in the sandbox, which is free, and subscribe again whenever TestFlight stops renewing it (it renews daily, up to 6 times). One build where a new sandbox install behaves the same as the App Store, but once someone has subscribed in the sandbox they're never locked out again. What do you do in your own apps, and what would you recommend? Has App Review ever pushed back on any of these? Thank you for any help.

Hello everyone, After waiting over a week in review, all of my recently submitted apps were rejected under Guideline 4.3 (Spam) and Guideline 4.2.6 (App Generation Services). The rejection messages are generic and do not specify which components, assets, or metadata triggered the flags. To clarify, these are original native apps built from scratch in Xcode/Swift—not commercialized templates, web wrappers, or third-party app generation builds—and each has distinct mechanics, custom assets, and functionality. I have already replied in the Resolution Center, submitted an official appeal/support inquiry, and requested an expedited review, but it has been 3 days with no response. Has anyone experienced false-positive 4.3/4.2.6 flags across multiple distinct apps on the same developer account, or can an Apple representative advise on what specific areas I should audit to get these resolved? Thank you in advance for your guidance.

Hello, Our app has been in "In Review" status since October 25, 2026 — 12 days now, with no messages or requests from App Review. App: Ryla: Photo Looks & Filters (Apple ID 6821447421) Submission ID: bbe1d65e-6429-4c33-9a25-7c2128f6c8a8 Items: version 1.0 (build 10), two auto-renewable subscriptions, a subscription group and three consumable in-app purchases Developer Support case: 103001645719 Timeline: Oct 12: first submission Oct 25: rejected under Guideline 1.1 (screenshots); we replaced the flagged screenshots and previews and resubmitted the same day Oct 25 → today: "In Review", no further updates We have also requested an expedited review and replied to our Developer Support case. Agreements, tax and banking are all active, and there are no unanswered messages in App Store Connect. Could someone from App Review please check whether this submission is stuck? We're happy to provide a demo video, test details or anything else needed right away. Thank you.

Hello, I am looking for advise and if anyone knows apple developer / app review team phone number, please help. I have submitted my app Day1Work on 15th October, App review team reviewed on 30th October and ask to provide some log in creds , which I provided and updated the app with what they were asking for. Since 30th of October till now there are no respose from the app review team, I have tried Expadited Review Request, wrote to support through the form, called 3 times general apple support team, but nothing , no update. If anyone is facing the similar issue , please share and what did you which helped later. Thank you for your attention. S.Howlader

I'm aware that Apple receives a high volume of app submissions, and I understand that the review process takes time. However, I've submitted expedited review requests due to a time-sensitive launch. Apple states that over 90% of app reviews are completed within 24–48 hours. Unfortunately, my submissions have consistently been taking approximately 168 hours (7 days) per review. Each time, I receive only 1–2 issues to address. After making the requested changes and resubmitting, I'm facing another 7-day wait, often for another 1–2 issues. I completely understand that apps must meet Apple's guidelines, and I'm more than willing to make any necessary changes. I'm simply trying to understand whether these extended review times are normal or if there may be something I'm doing incorrectly in the submission process. This is my first time submitting an app to the App Store, so I would sincerely appreciate any advice, insight, or feedback from those who have been through this process. Thank you!

I’m an individual developer with a live educational app for children aged 3 to 5 who can’t read yet. Everything in the app is spoken: instructions, feedback and task prompts are voice recordings. For a child who can’t read, the language isn’t a setting. It is the whole product. Current setup The app is Sovice, Croatian, live since October 2026, with native Croatian voice recordings and a Croatian curriculum. It’s currently Croatian only. I’m now preparing an English version for the US and UK. The problem with adding English to the same app The child can’t recover from the wrong language. With two languages in one app, a parent picking the wrong one, or the app ending up in one by accident, leaves a three-year-old who can’t read the screen to switch back. This applies both ways: a US child landing in Croatian and a Croatian child landing in English. The listing follows the device language, not the market. Many Croatian parents set their phones to English. With an English listing, they’d see an English app and miss that this is a Croatian app, even though the Croatian recordings are why they’d download it. The markets need different products. The English version would have a different curriculum (English phonics and early reading), its own brand and mascot, and features for US families, such as a homeschool parent mode. Croatian families need things US families don’t, and the other way round. What I’m considering Two separate single-language apps from one shared codebase, each with its own bundle ID, name, brand and content, and availability limited to its own markets: Sovice: Croatian, sold in Croatia and the region. Wise Beaks: English, sold in English-speaking countries. Questions Has anyone shipped separate language or market versions of a kids or education app without a 4.3(a) rejection? What differentiation did App Review accept? Does “the users can’t read, so each app must be single-language” help when explaining this to App Review, or is it irrelevant to 4.3(a)? If one app is the expected path: is there a way to show a specific product page per country regardless of device language?

I’d like to raise how our app’s review has gone, in the hope that someone at App Review sees it, and to ask whether other developers are seeing the same thing. Our app is Suan, a sleep audio app. It’s iPhone-only. It has no server and no account, and one auto-renewing yearly subscription shown with Apple’s own SubscriptionStoreView. What has happened: 30 Oct: submitted. 3 Nov: rejected under 5.1.1(iv) for the wording on our Apple Health screen. Fair enough. Fixed and resubmitted the same day. 5 Nov: rejected on three points: 5.1.1(iv) again, for a button label that was already there in the first review and wasn’t mentioned then; 2.1(b): the reviewer couldn’t find the In-App Purchase; 2.1(a): every audio download failed on an iPad Air (M3) on iPadOS 27. We fixed all three. Every track now ships inside the app, so nothing downloads at all. The review notes say step by step where the subscription is: it appears straight after onboarding, it’s the first section in Settings, and it opens when you tap play on any track. 8 Nov: rejected under 2.1(a) for “an error during onboarding”, again on the iPad Air (M3). The reviewer’s screenshot shows Apple’s SubscriptionStoreView reporting “NSURLErrorDomain error -1009”. That error means the device is not connected to the internet. The screen is Apple’s own, loading our subscription from the App Store sandbox. Our onboarding makes no network requests. So of the issues raised, two came from the review device having no connection, one was a subscription that the review notes explain how to find, and one was a button that passed the first review. None of them happen on our own iPhones. We’ve replied to every rejection in App Store Connect, and resubmitted each time within hours. The Android version of the same app, with the same features, content and subscription, went through Google Play’s review and was approved. Each round costs us two to three days, and we’ve now spent about two weeks on a launch that was ready at the start. I’d be grateful for a few things: When the error in a screenshot is a network error like -1009, could reviewers check the device’s connection, or try again, before rejecting? Could every issue be raised in one review, rather than a new one appearing after each fix? Could reviewers read the review notes? For us they answered the question the rejection asked. Has anyone else had StoreKit or network failures in review on iPad Air (M3) with iPadOS 27? I’ve seen a few threads describing the same thing. If anyone found a way past it, I’d love to hear it. The quality of the testing effort has been pretty poor. Thank you.

Hello, Our iOS app has been rejected four times under Guideline 2.1(a) because sign-in fails on the review iPad. The latest rejection showed NSURLErrorDomain error -1001 (the request timed out) on an iPad Air 11-inch (M3) with iPadOS 27.0, on November 5, 2026, at about 11:54 UTC. The same happened on October 16, 2026. Setup: API: https://wp.pavilion.az, HTTPS on port 443, fixed DNS name DNS and proxy on Cloudflare (IPv4 and IPv6), publicly trusted certificate The app uses URLSession, with no custom certificate checks and no proxy settings What we checked: Neither our origin server nor Cloudflare logged any request from the review device on either day. Other clients were served normally during the same minutes. The domain resolves normally from many public DNS resolvers in the United States and Europe, over IPv4 and IPv6. The app signs in in under one second on an iPad simulator in a data center in Los Angeles, and on our own devices through TestFlight. This looks similar to https://developer.apple.com/forums/thread/773444, where a Cloudflare-hosted domain resolved to a wrong address inside Apple's network. Could someone from Apple check how wp.pavilion.az resolves, and whether it is reachable, from the App Review network? We have resubmitted a build that adds a short network check to the error message (the DNS result and which connection step fails), but each review cycle takes many days. Thank you.

Our first submission has now been rejected under Guideline 2.1(b), with the message: "the in-app purchases do not load successfully." Each review was performed on an iPad Air 11-inch (M3) running iPadOS 26.6. The app sells only auto-renewable subscriptions. We cannot reproduce the failure, and we have verified every part of the configuration we can think of. WHAT WE VERIFIED (via the App Store Connect API, not just the UI) Two subscriptions in one group, state READY_TO_SUBMIT Product IDs exactly match what the app requests Available in 175 territories, including the United States Prices set, en-US localizations present for both products and for the group App review screenshots attached to both, state COMPLETE Both subscriptions are included in the review submission (READY_FOR_REVIEW) Paid Apps Agreement: Active. Bank account: Active. Tax forms: Active. WHAT WORKS On our own devices, installed via TestFlight (sandbox environment), the products load correctly and a purchase completes and activates as expected. This works on both a real Apple ID and a Sandbox Tester account. WHAT WE OBSERVED FROM THE REVIEW SESSION We use RevenueCat. Their server-side API returns our offering with both packages and the correct product identifiers, so the offering metadata is fine. Our backend also shows that the reviewer's session reached our servers and signed in successfully at the review timestamp, so the device had working network connectivity. That leaves StoreKit itself returning no products on the reviewer's device, which is what empties the offering. QUESTIONS Are there known conditions under which StoreKit returns no products in the App Review sandbox for subscriptions that are in "Ready to Submit" and are attached to the same submission as the binary? For an app that has never been approved, is product loading during review handled differently from a normal sandbox session on a released app? Is there any way to obtain diagnostics from a review session, or to ask the reviewer for a screenshot of the failing screen? Replies in Resolution Center so far have only repeated the original rejection text. Is there anything specific to iPadOS 26.6 that could affect StoreKit 2 product lookups? For the next submission we have added a timeout and automatic retries around the product lookup, plus a visible retry control instead of a spinner, in case the failure is a transient cold-start timeout. But we would rather understand the actual cause than keep guessing. Any pointers appreciated.

Hello Apple Developer Community, My first iOS app, PitCaptain, has been stuck in “Waiting for Review” since October 7, 2026. App: PitCaptain Version: iOS 1.0.0 (build 10) Submission date: October 7, 2026 Current status: Waiting for Review Expedited review: Requested Contacted Apple Support: Yes The app has not moved to “In Review”, and I have not received any feedback or requests for additional information. PitCaptain helps endurance racing teams plan driver changes, driving stints, refuelling windows and driver-change alarms. I understand that review times can vary, but nine days without any status change is concerning, especially after requesting an expedited review. Could someone from App Review please check whether the submission is progressing normally or whether it may be stuck in the review queue? Any advice or assistance would be greatly appreciated. Thank you!

Days and Days of Apple Review Delays — For Us, This Is Business, Not a Game! Sorry, Other Platforms Do It Better! We are deeply disappointed and frustrated by Apple's prolonged App Review process and the lack of effective communication and support. Developing applications is not a game. It is business. Behind every app there are professionals, investments, deadlines, commitments and projects that cannot remain on hold indefinitely. Apple offers telephone assistance to customers purchasing an iPhone, yet developers facing critical App Review issues often struggle to speak directly with someone capable of resolving them. How is it possible that a company of Apple's size cannot provide accessible, qualified telephone support to the professionals who contribute to its ecosystem? A simple conversation could resolve in minutes what currently takes days of emails, support tickets and repeated submissions. Equally frustrating is the practice of communicating review issues one at a time, across multiple review cycles, rather than providing a comprehensive list of concerns whenever possible. This fragmented approach wastes everyone's time, creates unnecessary delays and offers no meaningful solution. In our case, despite promptly addressing every request and receiving approval for an expedited review, our application remains in "Waiting for Review" as of November 13, 2026, without any substantive explanation or response to our repeated requests for assistance. And the consequences are real. We were forced to postpone our official launch, scheduled for November 11, 2026, disrupting months of preparation, promotional activities, editorial planning and professional commitments. Our application is already available on Android and other digital app stores. Apple's App Store is the only major distribution channel where our application is still missing. Our experience with these other platforms has been considerably more straightforward and cooperative. It is particularly frustrating that Apple, a global leader in technology, is the only platform preventing us from completing our planned digital launch. We fully respect Apple's quality and security standards. However, high standards should never become an excuse for inefficient communication or inadequate developer support. We are not asking for special treatment. We are asking for transparency, timely assistance and respect for the professional work carried out within Apple's ecosystem. And what exactly is Apple keeping on hold? Radio Quadraro, a new independent, nonprofit radio station based in Rome, created by professionals passionate about music, broadcasting and communication. Our application has one simple purpose: to allow people to listen to our radio station. Yet an entire radio launch has been postponed while we wait for an App Store review. Behind every application there is a real project. Behind every delay there are real consequences. We did not expect Apple to make an exception for us. We expected Apple to live up to its own standards. We request an immediate update, confirmation of our expedited review status and direct assistance from a qualified Apple representative. Radio Quadraro Team App ID: 6823630759 Apple Developer Support Case: 30000007065025

Hello, My first app (Apple ID: 6770062707), submitted on the 29th of october, was rejected on November 6 under Guideline 3.1.1. I resolved the issue by removing the external donation link and submitted a new build on November 7, together with an expedited review request. Since then, the submission has remained in "Waiting for Review" for more than 6 days, with no updates. I have also contacted App Review via the Contact Us form, but have not received a response. Submission ID: 7e55dc6a-55b7-4742-b699-5531d38f1a3e Version: 1.0 (48) Could someone from App Review please check whether anything is blocking this submission? Thank you, Zoltán Hidegkuti

Hi, I’m building a free educational ear-training app for social dancers (Education category, no ads, no in-app purchases). In this dance tradition, recognising the orchestra by ear is a practical skill, not trivia. Each historical orchestra has its own rhythm, phrasing and character, and dancers adapt their movement to it: crisp and rhythmic for one, smooth and flowing for another, with dramatic pauses for a third. At social dance events, the music is played in sets by a single orchestra, so identifying it in the first seconds tells dancers how to move. This skill cannot be learned from text, notation or descriptions alone. It is acquired only by listening to the actual recordings and repeatedly practising recognising them, which is why authentic audio is essential. Teachers train this skill in class, and the app makes it practicable at home. Users learn through a catalogue of orchestras with style descriptions (what to listen for and how it affects the dance), A/B listening comparisons and short exercises with spaced repetition. After each answer the app explains which musical features identify the orchestra. As listening material, the app plays the official 30-second previews from the iTunes Search API: streamed only, never downloaded, saved or cached, each preview shows “provided courtesy of iTunes”, each preview has the official “Listen on Apple Music” badge linking to the exact recording, so users can listen to the full track and add it to their library, previews are never used as background music. The Search API terms say previews may be used “only to promote store content and not for entertainment purposes”. Is an educational exercise like this acceptable promotional use under these terms, or is MusicKit required for this kind of app? Apple Developer Support (case 103008374208) suggested I ask here. Thank you!

Hello App Review team, I'm asking for help confirming that our escalated case is attached to our current submission. App: Upfora (iOS) App ID: 6812258703 Version: 3.4 Current submission: November 8, 2026, "Waiting for Review" since then Developer Support case: 102994003655 Background - First submitted September 15, 2026. This is our first App Store release; the app is already live on Google Play and on the web. - App Review has reviewed it twice: October 1 (demo login not working) and October 22 (reporting of user-generated content). Both issues were fixed and resubmitted the same day. - In between, we withdrew and resubmitted several times to ship fixes. I now understand that each resubmission reset our place in the queue, and that this accounts for much of the delay. That was our mistake. Current situation - Developer Support escalated our case in early November, while our October 31 submission was waiting. We then resubmitted on November 7 and November 8, before I understood the effect, so I'm concerned the escalation is tied to a submission that no longer exists. - We have made no changes since November 8 and will make none until the review is complete. - The demo account in the review notes is active, and the reporting feature requested in the last review is included in this build. My questions 1. Can the escalation on case 102994003655 be applied to the current November 8 submission? 2. Is there anything on our side (metadata, review notes, account) that is holding the submission? Thank you for your help. Nodirkhon Founder, Upfora

Hi everyone, My app has been stuck in "In Review" since November 1, 2026. It's been 12 days now with no updates or communication from Apple. The app hasn't been rejected and Apple hasn't reported any issues or requested any changes. I'm just waiting for the review to finish. I've also checked my app analytics and there has been no activity from reviewers since the app entered "In Review". I understand that not all review activity may be visible in analytics, but it makes me wonder if anyone has actually started reviewing it. I've contacted Apple Developer Support several times and even opened a new support ticket, but I still haven't received a response that addresses the issue. What's strange is that another app on the same developer account entered review on November 11 and was approved the same day. Has anyone else experienced something like this? Is there any other way to reach the App Review team or get someone to look into a stuck review? Any help would be appreciated. Thanks!